Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1001

reference
397-tree-1
name
1001
tree-preservation-order

undefined

397-tpo-1
uprn
address-text
point
POINT (-1.017741 50.894752)
geometry
MULTIPOLYGON (((-1.017613 50.894739,-1.017619 50.894764,-1.017637 50.894787,-1.017665 50.894805,-1.017700 50.894817,-1.017740 50.894821,-1.017779 50.894817,-1.017815 50.894806,-1.017844 50.894788,-1.017862 50.894766,-1.017869 50.894741,-1.017864 50.894716,-1.017846 50.894693,-1.017818 50.894675,-1.017782 50.894663,-1.017743 50.894659,-1.017703 50.894663,-1.017667 50.894674,-1.017639 50.894691,-1.017620 50.894714,-1.017613 50.894739)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL